About Exporting Files

You can export specific jobs, job groups, or calendars. You can also export multiple jobs and job groups or multiple calendars using a selection file that has been previously created in TA. For each of the jobs and job groups exported, all child jobs or job groups are exported recursively. Jobs that depend on the jobs are also exported.

Specifically, a job or job group export includes these referenced artifacts:

  • Job groups

  • Job classes

  • Events

  • Actions

  • Resources

  • Variables

  • Business views

In addition, these relationships are exported:

  • AlertAction

  • DependencyUnion

  • EmailAction

  • EventActionJoin

  • EventCalendarJoin

  • EventJobClassJoin

  • EventJobJoin

  • ITOAction

  • JESDependency

  • JobAction

  • JobDependency

  • LogAction

  • ResourceJobJoin

  • ResourceNodeJoin

  • ServiceAction

  • SNMPAction

  • VariableAction

  • VariableDependency

For calendars, all specified and related calendars are also exported:

  • Calendar groups

  • Calendar lists

  • Child calendars

  • Fiscal calendars

  • Included or excluded calendars

Static Artifacts

The names of the static artifacts are also exported so that the target environment can be checked for the presence of these artifacts at the time of import. Static artifacts are unchanging base artifacts that are expected to be present in the target environment when the job or job group is imported. Static artifacts are not imported.

The names of these static artifacts are exported with jobs or job groups:

  • Owner

  • User

  • Calendar

  • AgentList

  • ServiceAgentList

  • Node

  • Businessunit

  • Service

  • SystemValue

  • AgentListJoi

These static artifacts are exported with calendars:

  • Owner

  • User

  • AgentList

  • NodeList

The Export Workflow

When you export a given set of jobs, job groups, or calendars, this happens:

  1. The Export or Import utility attempts to connect to the source Client Manager. If the fails, the utility quits operation after logging an error.

  2. If the to the source Client Manager is successful, then the utility checks if the directory provided for export is empty. If not empty, the utility logs an error and quits operation.

  3. If the directory provided for export does not exist, the directory is created. The Export Import utility requires appropriate file system permissions to be able to create the directory

  1. Data is exported in XML format after transforming the raw data from TA to replace database IDs with their corresponding names.

  1. If an error is encountered during the export process, the utility quits processing. The utility does not clean or remove data that was already exported at the point of error; this is enables analysis of the error that occurred.

  2. Once the data is successfully exported to the file system as XML files, the utility writes a file named export.log to the export directory to record summary information about the export.

    The summary information in the export.log includes:

    • Type of export (job, calendar, job delta, or calendar delta)

    • A list of jobs or job-groups selected for export

    • The version of the TA Master

    • The time taken for export.

    • The export output has this directory structure:

Note: If any input is not valid, the utility halts processing after logging an appropriate error message.